-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] feat: copy log to central system #441
base: transition-to-runkit
Are you sure you want to change the base?
[WIP] feat: copy log to central system #441
Conversation
9d849f6
to
d86cc46
Compare
b056ea9
to
34a737c
Compare
a23c520
to
c101f33
Compare
be62e5a
to
49bb197
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure you got the change between the current log transfer and archiving schema and the new one we are moving towards too. Just to be sure we are all at the same page
Current: There is a central node (LogTransferManager) that runs in the master machine and periodically tells the slave machines process servers to send their logs to a target dir. Then, another tool (LogRuntimeArchive) gets the data accumulated in this target folder and does the archiving (compress and move to another storage)
New: The LogTransferManager is taken out the dynamic, and now the slave machines will have a client that periodically sends its logs to a LogTransferServer at the master machine. Then, the master machine LogRuntimeArchive continues to do what it currently does
Given that, I think a great way to test your implementation is to setup a server in your machine and a use a client to get files from on folder to another
This is clear to me. The biggest difficulty lies in implementing it. |
49bb197
to
987a361
Compare
There are unit tests for the current log transfer functionality. There should be unit tests for the new functionality as well. |
cc2964c
to
d9bebde
Compare
d9bebde
to
2d42928
Compare
2d42928
to
daf2442
Compare
No description provided.